Repository navigation
chore: add MCP Registry label and server.json - #420
Merged
Merged
Conversation
The official MCP Registry verifies an OCI image by the io.modelcontextprotocol.server.name label; server.json describes the image, its streamable-http MCP endpoint and the env that turns it on.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Prepares Buggregator for the official MCP Registry (other MCP catalogs such as PulseMCP and GitHub's registry read from it).
Dockerfile:LABEL io.modelcontextprotocol.server.name="io.github.buggregator/server"on the final image. The registry checks this label to confirm we own the OCI image.server.json: the registry entry. OCI packageghcr.io/buggregator/server, MCP over streamable HTTP on:8001(MCP_ENABLED=true,MCP_TRANSPORT=http), description 88 chars (limit 100). Validated against the2025-12-11schema.Nothing is published by this PR. Only images built after it carry the label, so the first publish must point at the next release tag;
versionandidentifierare set at publish time.Checked:
server.jsonvalidates against the registry schema (jsonschema);docker build --check .has no warnings. The image itself was not built here (CI does not build it; the release workflow does).Made with harnsy